fix(docs): make Linux tar log-collection commands actually work (#16)#36
Merged
dannyneira merged 1 commit intomainfrom May 8, 2026
Merged
fix(docs): make Linux tar log-collection commands actually work (#16)#36dannyneira merged 1 commit intomainfrom
dannyneira merged 1 commit intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Closes #16. The Linux tar commands in 'Gathering Warp Logs' fail with 'tar: warp.log*: Cannot stat: No such file or directory' on Linux: bash leaves the unmatched literal 'warp.log*' as the file argument to tar, and tar then looks for a literal file named 'warp.log*' inside the -C directory. Switch to 'cd into the directory first, then tar' so the shell expands the glob in the right pwd. Wrap the cd+tar in subshell parens so the user's pwd is preserved after the command finishes (the cd only affects the subshell). Verified with GNU tar 1.35 + bash: - OLD command reproduces the reporter's failure (exit=2, 'Cannot stat: No such file or directory'). - NEW command exits 0 and archives warp.log, warp.log.1, warp.log.2. - Caller's pwd is unchanged after the subshell exits. (Earlier draft of this fix used GNU tar's --wildcards flag, but --wildcards only enables glob matching during EXTRACTION/listing; in creation mode tar still treats arguments as literal paths. Reverted to the cd-then-tar approach the issue reporter suggested.) Also normalize the indentation in the Linux :::caution RUST_LOG block to the 4-space indent already used by the macOS and Windows tabs. Co-Authored-By: Oz <oz-agent@warp.dev>
hongyi-chen
force-pushed
the
oz/fix-16-linux-tar-glob
branch
from
0e6ed75 to
f9fd8fa
Compare
dannyneira
approved these changes
May 8, 2026
Member
dannyneira
left a comment
dannyneira
left a comment
There was a problem hiding this comment.
Tested and confirmed working in bash, zsh, and pwsh on Linux
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #16.
Problem
The Linux tar commands in Gathering Warp Logs at
src/content/docs/support-and-community/troubleshooting-and-support/sending-us-feedback.mdx(L161, L169) fail withtar: warp.log*: Cannot stat: No such file or directory. On Linux with bash + defaultnullglob=off, an unmatchedwarp.log*glob is left as a literal argument; tar then looks for a literal file namedwarp.log*inside the-Cdirectory and fails. Reported in #16.The macOS (
zip -j) and Windows (Compress-Archive) commands aren't affected — only the Linux tab.Fix
cdinto the log directory first, so the shell expands the glob in the right pwd. Wrap thecd+tarin subshell parens so the user's pwd is preserved after the command finishes:While I was in the file, also normalized the indentation in the Linux
:::cautionRUST_LOG=…block to the 4-space indent already used by the macOS and Windows tabs.Verification
Reproduced the bug + verified the fix with GNU tar 1.35 + bash on a sandbox dir:
gtar: warp.log*: Cannot stat: No such file or directory(exit=2).warp.log,warp.log.1,warp.log.2.before == afterafter the subshell exits.npm run buildsucceeds (315 pages).Conversation: https://staging.warp.dev/conversation/fddc3534-3d55-4783-a388-a1eb70e432f9
Plans:
This PR was generated with Oz.